The CICA Windows Explosion!

home *** CD-ROM | disk | FTP | other *** search

/ The CICA Windows Explosion! / The CICA Windows Explosion! - Disc 2.iso / demo / wemdemo4.zip / INFO / W3.3 (.txt) < prev next >

Wrap

GNU Info File | 1994-09-21 | 48KB | 877 lines

This is Info file ../info/w3, produced by Makeinfo-1.56 from the input file w3.txi. This file documents the Emacs-w3 World Wide Web browser. Copyright (C) 1993, 1994 William M. Perry Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. File: w3, Node: Using PGP/PEM, Next: Native WAIS Support, Prev: Interfacing to GNUS, Up: Advanced Features Using PGP/PEM ============= Most of this section was taken from the documentation written by Rob McCool robm@ncsa.uiuc.edu. Gratefully reproduced here with permission from him.(1). RIPEM is 'Riordan's Internet Privacy Enhanced Mail', and is currently on version 1.2b3. If you are a US citizen, you can ftp it from ripem.msu.edu:/pub/crypt/ripem. PGP is 'Pretty Good Privacy', and is currently on version 2.6. The legal controversies that plagued earlier versions have been resolved, so this is a competely legal program now. There is also a legal version for eurpoean users, called 2.6ui (the Unofficial International version). PGP and PEM are programs to allow you and a second party to communicate in a way which does not allow third parties to read them, and which certify that the person who sent the message is really who they claim they are. PGP and PEM both use RSA encryption. The U.S. government has strict export controls over foreign use of this technology, so people outside the U.S. may have a difficult time finding programs which perform the encryption. You will need a working copy of either Pretty Good Privacy or RIPEM to begin with. You should be familiar with the program and have generated your own public/private key pair. You should be able to use the TIS/PEM program with the PEM authorization type. I haven't tried it. This tutorial is written assuming that you are using RIPEM. Currently, the protocol has been implemented with PEM and PGP using local key files on the server side, and on the client side with PEM using finger to retrieve the server's public key. As you can tell, parties who wish to use Emacs-w3 and httpd with PEM or PGP encryption will need to communicate beforehand and find a tamper-proof way to exchange their public keys. Pioneers get shot full of arrows. This work is currently in the experimental stages and thus may have some problems that I have overlooked. The only known problem that I know about is that the messages are currently not timestamped. This means that a malicious user could record your encrypted message with a packet sniffer and repeat it back to the server ad nauseum. Although they would not be able to read the reply, if the request was something you were being charged for, you may have a large bill to pay by the time they're through. This protocol is almost word-for-word a copy of Tony Sander's RIPEM based scheme, generalized a little. Below, wherever you see PEM you can replace it with PGP and get the same thing. *Client:* GET /docs/protected.html HTTP/1.0 UserAgent: Emacs-W3/2.1.x *Server:* HTTP/1.0 401 Unauthorized WWW-Authenticate: PEM entity="webmaster@hoohoo.ncsa.uiuc.edu" Server: NCSA/1.1 *Client:* GET / HTTP/1.0 Authorization: PEM entity="robm@ncsa.uiuc.edu" Content-type: application/x-www-pem-request --- BEGIN PRIVACY-ENHANCED MESSAGE --- this is the real request, encrypted --- END PRIVACY-ENHANCED MESSAGE --- *Server:* HTTP/1.0 200 OK Content-type: application/x-www-pem-reply --- BEGIN PRIVACY-ENHANCED MESSAGE --- this is the real reply, encrypted --- END PRIVACY-ENHANCED MESSAGE --- That's it. Emacs-w3 uses the excellent mailcrypt package written by Jin S Choi jsc@mit.edu.(2). This package takes care of calling ripem and/or pgp with the correct arguments. Please see the documentation at the top of mailcrypt.el for instructions on using mailcrypt. All bug reports about mailcrypt should go to Jin S Choi, but bugs about how I use it in Emacs-w3 should of course be directed to me. ---------- Footnotes ---------- (1) See http://hoohoo.ncsa.uiuc.edu/docs/PEMPGP.html (2) Available via anonymous ftp to archive.cis.ohio-state.edu:/pub/gnu/emacs/elisp-archive/interfaces/mailcrypt.el.Z File: w3, Node: Native WAIS Support, Next: Rating Links, Prev: Using PGP/PEM, Up: Advanced Features Native WAIS Support =================== :: WORK :: File: w3, Node: Rating Links, Next: Gopher Plus Support, Prev: Native WAIS Support, Up: Advanced Features Rating Links ============ The `w3-link-delimiter-info' variable can be used to 'rate' a URL when it shows up in an HTML page. If non-`nil', then this should be a list specifying (or a symbol specifying the name) of a function. This function should expect one argument, a fully specified URL, and should return a string. This string is inserted after the link text. If a user has decided that all links served from blort.com are too laden with images, and wants to be warned that a link points at this host, they could do something like this: (defun check-url (url) (if (string-match "://[^/]blort.com" url) "[SLOW!]" "")) (setq w3-link-delimiter-info 'check-url) So that all links pointing to any site at blort.com shows up as "Some link[SLOW!]" instead of just "Some link". File: w3, Node: Gopher Plus Support, Next: Hooks, Prev: Rating Links, Up: Advanced Features Gopher+ Support =============== :: WORK :: File: w3, Node: Hooks, Next: Other Variables, Prev: Gopher Plus Support, Up: Advanced Features Hooks ===== These are the various hooks you can use to customize some of Emacs-w3s behavior. They are arranged in the order in which they would happen when retrieving a document. All of these are functions (or lists of functions) that are called consecutively. `w3-load-hooks' These hooks are run by `w3-do-setup' the first time a URL is fetched. All the w3 variables are initialized before this hook is run. `w3-file-done-hooks' These hooks are run by `w3-prepare-buffer' after all parsing on a document has been done. All `url-current-'* and `w3-current-'* variables are initialized when this hook is run. This is run before the buffer is shown, and before any inlined images are downloaded and converted. `w3-file-prepare-hooks' These hooks are run by `w3-prepare-buffer' before any parsing is done on the HTML file. The HTTP/1.0 headers specified by `w3-show-headers' have been inserted, the syntax table has been set to `w3-parse-args-syntax-table', and any personal annotations have been inserted by the time this hook is run. `w3-mode-hooks' These hooks are run after a buffer has been parsed and displayed, but before any inlined images are downloaded and converted. File: w3, Node: Other Variables, Prev: Hooks, Up: Advanced Features Miscellaneous variables ======================= There are lots of variables that control the real nitty-gritty of Emacs-w3 that the beginning user probably shouldn't mess with. Here they are. `w3-icon-directory-list' A list of directorys to look in for the w3 standard icons... must end in a /! If the directory `data-directory'/w3 exists, then this is automatically added to the default value of http://cs.indiana.edu/elisp/w3/icons/. `w3-keep-old-buffers' Whether to keep old buffers around when following links. If you do not like having lots of buffers in one Emacs session, you should set this to `nil'. I recommend setting it to `t', so that backtracking from one link to another is faster. `url-passwd-entry-func' This is a symbol indicating which function to call to read in a password. It is set up depending on whether you are running "EFS" or "ange-ftp" at startup if it is `nil'. This function should accept the prompt string as its first argument, and the default value as its second argument. `w3-reuse-buffers' Determines what happens when `w3-fetch' is called on a document that has already been loaded into another buffer. Possible values are: `nil', `yes', and `no'. `nil' will ask the user if Emacs-w3 should reuse the buffer (this is the default value). A value of `yes' means assume the user wants to always reuse the buffer. A value of `no' means assume the user always wants to re-fetch the document. `w3-show-headers' This is a list of HTTP/1.0 headers to show at the end of a buffer. All the headers should be in lowercase. They is inserted at the end of the buffer in a <UL> list. Alternatively, if this is simply `t', then all the HTTP/1.0 headers are shown. `w3-show-status, url-show-status' Whether to show progress messages in the minibuffer. `w3-show-status' controls if messages about the parsing are displayed, and `url-show-status' controls if a running total of the number of bytes transferred is displayed. These Can cause a large performance hit if using a remote X display over a slow link, or a terminal with a slow modem. `url-uncompressor-alist' An assoc list of file extensions and the appropriate uncompression programs for each. This is used to build the Accept-encoding header for HTTP/1.0 requests. `url-waisq-prog' Name of the waisq executable on this system. This should be the `waisq' program from think.com's wais8-b5.1 distribution. File: w3, Node: More Help, Next: Future Directions, Up: Top More Help ********* If you need more help on Emacs-w3, please send me mail (wmperry@spry.com). Several discussion lists have also been created for Emacs-w3. To subscribe, send mail to <listname>-request@indiana.edu. All other mail should go to <listname>@indiana.edu. * w3-announce - this list is for anyone interested in Emacs-w3, and should in general only be used by me. The gnu.emacs.sources newsgroup and a few other mailing lists are included on this. You may use this if you have written an enhancement to Emacs-w3 that you wish more people to know about. (www-announce@info.cern.ch is included on this list). * w3-beta - this list is for beta testers of Emacs-w3. These brave souls test out not-quite stable code. * w3-dev - a list consisting of myself and a few other people who are interested in the internals of Emacs-w3, and doing active development work. Pretty dead right now, but I hope it will grow. If you need more help on the World Wide Web in general, please refer to the newsgroup comp.infosystems.www. There are also several discussion lists concerning the Web. Send mail to listserv@info.cern.ch with a subject line of 'subscribe <listname>'. All mail should go to <listname>@info.cern.ch. Administrative mail should go to www-admin@info.cern.ch. The lists are: * www-talk - for general discussion of the World Wide Web, where its going, new features, etc. All the major developers are subscribed to this list. * www-announce - for announcements concerning the World Wide Web. Server changes, new servers, new software, etc. As a last resort, you may always mail me. I'll try to answer as quickly as I can. File: w3, Node: Future Directions, Next: Programming Interface, Prev: More Help, Up: Top Future Directions ***************** Changes are constantly being made to the Emacs browser (hopefully all for the better). This is a list of the things that are being worked on right now. Fix before 2.3 1. Finish the native WAIS support. 2. New display engine 3. Correct imagemap capabilities. 4. Imagemap extensions (drag areas) 5. PATHs 6. TABLEs Long range goals 1. Multi-DTD browsing 2. Style sheets File: w3, Node: Programming Interface, Next: Generalized ZONES, Prev: Future Directions, Up: Top Internals of Emacs-w3 ********************* This chapter attempts to explain some of the internal workings of Emacs-w3 and various data structures that are used. It also details some functions that are useful for using some of the Emacs-w3 functionality from within your own programs, or extending the current capabilities of Emacs-w3. * Menu: * Generalized ZONES:: A generic interface to 'zones' of text that can contain information. * Global Variables:: Global variables used throughout Emacs-w3 * Data Structures:: The various data structures used in Emacs-w3 * Miscellaneous Functions:: Miscellaneous functions you can use to interface with w3 and access its data structures * MIME functions:: MIME functions--parsing messages, mailcap files, and more. File: w3, Node: Generalized ZONES, Next: Global Variables, Prev: Programming Interface, Up: Programming Interface Programming Interface Generalized ZONES ================= Due to the many different flavors of Emacs in existence, the addition of data and font information to arbitrary regions of text has been generalized. The following functions are defined for using/manipulating these "zones" of data. `w3-add-zone (start end style data &optional highlight)' This function creates a zone between buffer positions start and end, with font information specified by style, and a data segment of data. If the optional argument highlight is non-`nil', then the region highlights when the mouse moves over it. `w3-zone-at (point)' Returns the the zone at POINT. Preference is given to hypertext links, then to form entry areas, then to inlined images. So if an inlined image was part of a hypertext link, this would always return the hypertext link. `w3-zone-data (zone)' Returns the zone's data segment. The data structures used in Emacs-w3 are relatively simple. They are just list structures that follow a certain format. The two main data types are "form objects", "link objects",and "inlined images". All the information for these types of links are stored as lists. `w3-zone-hidden-p (zone)' Returns `t' if and only if a zone is currently invisible. `w3-hide-zone (start end)' Makes a region of text from `start' to `end' invisible. `w3-unhide-zone (start end)' Makes a region of text from `start' to `end' visible again. `w3-zone-start (zone)' Returns an integer that is the start of zone, as a buffer position. In Emacs 18.xx, this returns a marker instead of an integer, but it can be used just like an integer. `w3-zone-end (zone)' Returns an integer that is the end of zone, as a buffer position. In Emacs 18.xx, this returns a marker instead of an integer, but it can be used just like an integer. `w3-zone-eq (zone1 zone2)' Returns `t' if and only if zone1 and zone2 represent the same region of text in the same buffer, with the same properties and data. `w3-delete-zone (zone)' Removes zone from its buffer (or current buffer). The return value is irrelevant, and varies for each version of Emacs. `w3-all-zones ()' Returns a list of all the zones contained in the current buffer. Useful for extracting information about hypertext links or form entry areas. Programs should not rely on this list being sorted, as the order varies with each version of Emacs. `w3-zone-at (pt)' This returns the zone at character position PT in the current buffer that is either a link or a forms entry area. Returns `nil' if no link at point. These data structures are what is generally returned by `w3-zone-data'. File: w3, Node: Global Variables, Next: Data Structures, Prev: Generalized ZONES, Up: Programming Interface Global variables ================ There are also some variables that may be useful if you are writing a program or function that interacts with Emacs-w3. All of the `w3-current-*' variables are local to each buffer. `w3-current-mime-headers' An assoc list of all the MIME headers for the current document. Keyed on the lowercase MIME header (e.g., `content-type' or `content-encoding'. `w3-current-server' Server that the current document was retrieved from. `w3-current-file' Filename of the current document `w3-current-type' A string representing what network protocol was used to retrieve the current buffer's document. Can be one of http, gopher, file, ftp, news, or mailto. `w3-current-port' Port # of the current document. `w3-current-last-buffer' The last buffer seen before this one. `w3-running-FSF19' This is `t' if and only if we are running in FSF Emacs 19. `w3-running-epoch' This is `t' if and only if we are running in Epoch 4.x `w3-running-lemacs' This is `t' if and only if we are running in Lucid Emacs 19.6 or Lucid Emacs 19.8. `w3-running-new-lucid' This is `t' if and only if we are running in Lucid Emacs 19.9 or later. File: w3, Node: Data Structures, Next: Miscellaneous Functions, Prev: Global Variables, Up: Programming Interface Data Structures =============== Form objects are used to store information about a FORM data entry area. 1. `'w3form' 2. A cons pair of (METHOD . URL), where METHOD specifies what method to use to retrieve the form when it is submitted (e.g., `GET') and URL is a fully specified URL pointing at where to submit the FORM data to. 3. The type of input area this is. (e.g., `CHECKBOX' or `RADIO') 4. The name of the input tag. This is used when sending the form to the server, so that the server can tell what data is what. 5. The default value of the input area. Gotten from the INPUT tag at creation time. 6. The current value of the input area. 7. Whether the item is checked or not. Only used for RADIO or CHECKBOX items. 8. The size (in characters) of the input area. Not used for CHECKBOX, RADIO, or TEXTAREA input areas. 9. The maximum length of the input. Only used for TEXT or PASSWORD input areas. 10. The form that this input area belongs to. Each form in the same buffer has a unique identifier assigned when the document is parsed. It is used when the form is submitted to get only the data for the correct form. 11. A list of strings that represent the choices for this input area. Only used for SELECT tags. A new development in the World Wide Web is the concept of collapsible areas of text. If a zone controls one of these regions, it is marked with the w3expandlist property. The format of this structure is: 1. `'w3expandlist' 2. A marker representing the start of the hidden text as a buffer position. 3. A marker representing the end of the hidden text as a buffer position. A zone with the w3graphic property is a link to an inlined image's source file. 1. `'w3graphic' 2. The full URL of the inlined image. This is only ever returned if the inlined image is the only extent under point, or `w3-follow-inlined-image' is invoked. A zone with the w3 property is a full-fledged hypertext link to another document. 1. `'w3' 2. The ID attribute of this link. Used for resolving references to specific points within a document (e.g., `file.html#sectionA'. 3. The HREF attribute of this link. This is a fully specified URL pointing at a network resource. All relative directory references should have been removed before being stored in this structure. 4. The text between the <A> and </A> tags. This is used to build menus or to get the text of a link without doing a buffer-substring. 5. The URN attribute of this link. Currently not used for anything, waiting for the URN specification to be hammered out. 6. The REL attribute of this link. Specifies the links relevance to the current document. 7. The REV attribute of this link. Specifies the current documents relevance to the link. 8. The METHODS attribute, which tells what methods can be used on this link. (e.g., `GET, HEAD, PUT'. File: w3, Node: Miscellaneous Functions, Next: MIME functions, Prev: Data Structures, Up: Programming Interface Miscellaneous Functions ======================= I have done quite a bit of work trying to make a semi-clean interface to the internals of Emacs-w3. Here is a list of functions that you can use to take advantage of the World Wide Web. `w3-clear-tmp-buffer' Sets the current buffer to be `w3-working-buffer', creating it if necessary, and erase it. This should usually be called before retrieving URLs. `w3-convert-html-to-latex' Takes a buffer of HTML markup (which should be in `w3-working-buffer'), and convert it into LaTeX. This is an adaptation of the simple sed scripts from Cern. Does as good a job as the html2latex program, and I usually prefer its formatting over html2latex's. `w3-fetch' This function takes a URL as its only argument. It then attempts to retrieve the URL using the specified method, using data (if any) as the body of the MIME request. For example: `(w3-fetch "http://cs.indiana.edu/")' would retrieve the Indiana University CS home page and parse it as HTML. `w3-fix-entities-in-string' This function takes a string, and removes all HTML[+] entity references from it, replacing them with the correct character(s). It consults the variable `w3-html-entities' for the entity names and translations. For example, `(w3-fix-entities-in-string ">testing<&")' would return `">testing<&"'. `w3-generate-new-buffer-name' This function takes a string, and returns the first unique buffer name using that string as a base. For example `(w3-generate-new-buffer-name "new-buff")' would return `"new-buff<1>"' if buffer `new-buff' already existed. `w3-generate-unique-filename' This functions returns a string that represents a unique filename in the /tmp directory. For example, `(w3-generate-unique-filename)' would return `"/tmp/w3-tmp129440"'. The filename is arrived at by using a unique prefix (w3-tmp), the uid of the current user (12944 in my case), and a number that is incremented if a file already exists. `w3-buffer-visiting (url)' Return the name of a buffer (if any) that is visiting URL. `w3-create-mime-request (fname ref-url)' Create a MIME request for the file fname. The Referer: field of the HTTP/1.0 request is set to the value of ref-url if necessary. Returns a string that can be sent to an HTTP server. The request uses several variables that control how the request looks. If the value of `url-current-server' is found in the assoc list of `url-bad-server-list', then the basic HTTP/0.9 request type is used. This loses lots of information and server-side typing of files, but it is necessary for some older HTTP/0.9 servers that can't understand the newer, longer HTTP/1.0 requests. If the value of `url-request-extra-headers' is non-`nil', then it is used as extra MIME headers when an HTTP/1.0 request is created. `url-get-url-at-point' This function returns the url at a point specified by an optional argument. If no argument is given to the function (point) is used. Tries to find the url closest to that point, but does not change the users position in the buffer. Has a preference for looking backward when not directly on a URL. `w3-hexify-string' This function takes a string and replaces any characters that are not acceptable in a URL with the "escaped" encoding that is standard for URLs (replaces the character with a % followed by the hexadecimal representation of the ASCII value of the character). For example, `(w3-hexify-string "this is a test")' would return `"this%20is%20a%20test"'. `w3-insert-entities-in-string' This function takes a string and replaces any occurences of HTML[+] reserved characters with the corresponding entity definitions. For example, `(w3-insert-entities-in-string "<testing>")' would return `"<testing>"'. `url-open-stream' This function takes the same parameters as `open-network-stream', and functions similarly. It takes a process name, a buffer name, a host name, and a port number or server name. It attempts to open a network connection to the remote host on the specified port/service name, with output going to the buffer. It returns the process object that is the network connection. `url-retrieve' This function takes 3 arguments, a URL, a method type, and a data block. It then attempts to retrieve the URL using the specified method, using data (if any) as the body of the MIME request. For example: `(w3-fetch "http://cs.indiana.edu/" "GET" nil)' would retrieve the Indiana University CS home page. This function does no parsing of the retrieved page, and leaves you in the buffer containing the document you requested. Any HTTP/1.0 redirection/authorization is done before this function exits. `w3-unhex-string' This is the opposite of `w3-hexify-string'. It removes any %XXX encoded characters in a string. For example `(w3-unhex-string "this%20is%20a%20test")' would return `"this is a test"'. `w3-upcase-region' This function takes a start and end position in the current buffer as its arguments, and converts all the text to uppercase, except for text between < and >, and it also ignores HTML[+] entity references (e.g., `<'). This is useful for converting regions to uppercase without corrupting any URLs within it. `w3-view-this-url' This function returns the URL of the zone under point (if no zone is under point, then it returns `nil'). If the optional argument is `nil', then the URL is also displayed in the minibuffer. `url-view-url' This function returns the URL of current document. If the optional argument is `nil', then the URL is also displayed in the minibuffer. File: w3, Node: MIME functions, Next: Concept Index, Prev: Miscellaneous Functions, Up: Programming Interface MIME Functions ============== `mm-compose-type(TYPE)' Compose a body section of MIME-type TYPE. This uses the compose field of a mailcap entry to generate the data, and returns a string that contains the data, with a correct content-type header. `mm-extension-to-mime(EXTN)' Return the MIME content-type of the file extension EXTN `mm-mime-info(ST ND REQUEST)' Get the mime viewer command for a specific MIME type. If ST is a number, then the MIME type is the `buffer-substring' between ST and ND, otherwise ST should be a string specifying the MIME type and associated data. Returns `nil' if the specified type is not found. Expects a complete content-type header line as its argument. This can be simple like text/html, or complex like text/plain; charset=blah; foo=bar Third argument REQUEST specifies what information to return. If it is `nil' or the empty string, the viewer (second field of the mailcap entry) is returned. If it is a string, then the mailcap field corresponding to that string is returned (print, description, whatever). If a number, then all the information for this specific viewer is returned. `mm-parse-mailcap(FILE)' Parse the mailcap file specified by FILE. `mm-parse-mailcaps(PATH)' Parse the default mailcap files. Optional argument PATH specifies a UNIX-style path of where to find the mailcap files. This function must be run before the rest of the mm-* functions. `mm-parse-mimetype-file(FILE)' Parse out a mime-types file specified by FILE. `mm-parse-mimetypes(PATH)' Parse the default mimetypes files. Optional argument PATH specifies a UNIX-style path of where to find the mimetypes files. File: w3, Node: Concept Index, Next: Key Index, Prev: MIME functions, Up: Top Concept Index ************* * Menu: * Annotations: Annotations. * ASK blocks: General Formatting. * Broken SUN libc: Firewalls. * Can't resolve hostnames: Firewalls. * Colors: Controlling Formatting. * Completion of URLs: Global History. * Connections hanging with lemacs & solaris: Firewalls. * Creating an HTTP request: Miscellaneous Functions. * Creating w3-emacs19-hack-XXX functions: Smart terminals. * Customizing formatting: Controlling Formatting. * Depth-first search: Searching. * Emacs 19.22 on terminals: Smart terminals. * Encryption: Using PGP/PEM. * Faulty hostname resolvers: Firewalls. * Firewalls: Firewalls. * Fonts: Controlling Formatting. * Forms based searching: Basic Setup. * Gateways: Firewalls. * GNUS: Interfacing to GNUS. * Gopher+: Basic Setup. * Gopher+: General Formatting. * Group Annotations: Group Annotations. * Hair-pulling gateway-headaches: Firewalls. * Highlighting on new terminals: Smart terminals. * Highlighting on terminals: Smart terminals. * History Lists: Session History. * Hooks: Hooks. * Host-based gateways: Firewalls. * HTML+: Markup Languages Supported. * Images: Inlined images. * Inlined images: Inlined images. * Inlined MPEGs: Inlined images. * Interfacing to GNUS: Interfacing to GNUS. * Interfacing to RMAIL: Interfacing to RMAIL. * Interfacing to VM: Interfacing to VM. * Internals of Emacs-w3: Programming Interface. * ISINDEX handling: Basic Setup. * Lucid Emacs & Solaris network problems: Firewalls. * Mailcrypt: Using PGP/PEM. * mime-types file: Adding MIME types based on file extensions. * Movies: Inlined images. * MPEGs: Inlined images. * Netpbm: Inlined images. * Network Protocols: Supported Protocols. * Newsgroups: More Help. * NeXTstep resources: Graphics workstations. * Pbmplus: Inlined images. * Personal Annotations: Personal Annotations. * PGP: Using PGP/PEM. * Pretty Good Privacy: Using PGP/PEM. * Protocols Supported: Supported Protocols. * Public Key Cryptography: Using PGP/PEM. * Recursive searching: Searching. * Relevant Newsgroups: More Help. * Retrieving Emacs-w3: Setting Up. * RIPEM: Using PGP/PEM. * RMAIL: Interfacing to RMAIL. * Searching more than one node: Searching. * Searching with forms: Basic Setup. * Security: Using PGP/PEM. * Setting Up Emacs-w3: Setting Up. * Solaris networking problems: Firewalls. * Specifying Fonts: Controlling Formatting. * Support: More Help. * Supported Protocols: Supported Protocols. * TERM: Firewalls. * Text highlighting on terminals: Smart terminals. * Usefulness of global history: Global History. * Usenet meets Emacs-w3: Interfacing to GNUS. * Using Emacs-w3 from your own programs: Programming Interface. * Using Emacs-w3 with RMAIL: Interfacing to RMAIL. * Using Emacs-w3 with VM: Interfacing to VM. * Using GNUS and Emacs-w3: Interfacing to GNUS. * VM: Interfacing to VM. * VTx00 terminals: Smart terminals. * World Wide Web: Introduction. * Xresources: Graphics workstations. File: w3, Node: Key Index, Next: Command Index, Prev: Concept Index, Up: Top Key Index ********* * Menu: * <: Movement. * >: Movement. * a: Hotlist Handling. * B: Action. * b: Movement. * button2: Action. * C-button2: Action. * C-c C-b: Action. * C-k: Information. * C-o: Action. * d: Hotlist Handling. * DEL: Movement. * F: Action. * f: Movement. * g: Action. * H: Movement. * H: Hotlist Handling. * k: Information. * K: Information. * l: Action. * m: Movement. * m: Action. * M-M: Miscellaneous. * M-m: Miscellaneous. * M-return: Action. * M-s: Action. * M-tab: Miscellaneous. * M-x w3-hotlist-refresh: Hotlist Handling. * M-x w3-insert-formatted-url: Miscellaneous. * n: Movement. * o: Action. * p: Miscellaneous. * P: Miscellaneous. * Q: Action. * q: Action. * r: Action. * return: Action. * s: Information. * S: Information. * SPC: Movement. * U: Miscellaneous. * V: Information. * v: Information. File: w3, Node: Command Index, Next: Variable Index, Prev: Key Index, Up: Top Command Index ************* * Menu: * lpr-buffer: Miscellaneous. * mm-parse-mimetypes: Adding MIME types based on file extensions. * scroll-down: Movement. * scroll-up: Movement. * system-name: Basic Setup. * url-create-mime-request: Miscellaneous Functions. * url-get-url-at-point: Miscellaneous Functions. * url-open-stream: Miscellaneous Functions. * url-retrieve: Miscellaneous Functions. * url-view-url: Information. * url-view-url: Miscellaneous Functions. * user-real-login-name: Basic Setup. * w3-add-personal-annotation: Personal Annotations. * w3-add-zone: Generalized ZONES. * w3-all-zones: Generalized ZONES. * w3-back-link: Movement. * w3-backward-in-history: Session History. * w3-backward-in-history: Action. * w3-buffer-visiting: Miscellaneous Functions. * w3-clear-tmp-buffer: Miscellaneous Functions. * w3-complete-link: Movement. * w3-complete-link: Action. * w3-convert-html-to-latex: Miscellaneous Functions. * w3-delete-personal-annotation: Personal Annotations. * w3-delete-zone: Generalized ZONES. * w3-emacs19-hack-TERMINAL: Smart terminals. * w3-emacs19-unhack-faces: Smart terminals. * w3-end-of-document: Movement. * w3-fetch: Miscellaneous Functions. * w3-fetch: Action. * w3-fetch: Session History. * w3-fix-entities-in-string: Miscellaneous Functions. * w3-follow-inlined-image: Data Structures. * w3-follow-inlined-image: Action. * w3-follow-link: Action. * w3-follow-mouse: Action. * w3-forward-in-history: Session History. * w3-forward-in-history: Action. * w3-forward-link: Movement. * w3-generate-new-buffer-name: Miscellaneous Functions. * w3-generate-unique-filename: Miscellaneous Functions. * w3-goto-last-buffer: Action. * w3-hexify-string: Miscellaneous Functions. * w3-hide-zone: Generalized ZONES. * w3-hotlist-add-document: Hotlist Handling. * w3-hotlist-delete: Hotlist Handling. * w3-hotlist-refresh: Hotlist Handling. * w3-hotlist-rename-entry: Hotlist Handling. * w3-insert-entities-in-string: Miscellaneous Functions. * w3-insert-formatted-url: Miscellaneous. * w3-insert-this-url: Miscellaneous. * w3-leave-buffer: Action. * w3-mail-current-document: Miscellaneous. * w3-mail-document-under-point: Miscellaneous. * w3-open-local: Action. * w3-print-this-url: Miscellaneous. * w3-print-url-under-point: Miscellaneous. * w3-quit: Action. * w3-reload-document: Action. * w3-save-this-url: Information. * w3-save-url: Information. * w3-search: Action. * w3-show-history: Session History. * w3-show-history-list: Action. * w3-show-hotlist: Movement. * w3-show-hotlist: Hotlist Handling. * w3-source-document: Information. * w3-source-document-at-point: Information. * w3-start-of-document: Movement. * w3-unhex-string: Miscellaneous Functions. * w3-unhide-zone: Generalized ZONES. * w3-upcase-region: Character based terminals. * w3-upcase-region: Miscellaneous Functions. * w3-use-hotlist: Hotlist Handling. * w3-use-hotlist: Movement. * w3-use-links: Miscellaneous. * w3-view-this-url: Miscellaneous Functions. * w3-view-this-url: Information. * w3-zone-at: Generalized ZONES. * w3-zone-data: Generalized ZONES. * w3-zone-data: Generalized ZONES. * w3-zone-end: Generalized ZONES. * w3-zone-eq: Generalized ZONES. * w3-zone-hidden-p: Generalized ZONES. * w3-zone-start: Generalized ZONES. * window-width: Basic Setup. File: w3, Node: Variable Index, Prev: Command Index, Up: Top Variable Index ************** * Menu: * fill-column: General Formatting. * lpr-command: Miscellaneous. * lpr-switches: Miscellaneous. * mm-mime-data: Specifying Viewers. * mm-mime-extensions: Adding MIME types based on file extensions. * tab-stop-list: General Formatting. * tab-width: General Formatting. * url-bad-port-list: Basic Setup. * url-bad-server-list: Miscellaneous Functions. * url-be-asynchronous: Basic Setup. * url-current-server: Miscellaneous Functions. * url-gateway-handholding-login-regexp: Firewalls. * url-gateway-handholding-password-regexp: Firewalls. * url-gateway-host: Firewalls. * url-gateway-host-password: Firewalls. * url-gateway-host-program: Firewalls. * url-gateway-host-program: Firewalls. * url-gateway-host-program-ready-regexp: Firewalls. * url-gateway-host-prompt-pattern: Firewalls. * url-gateway-host-username: Firewalls. * url-gateway-local-host-regexp: Firewalls. * url-gateway-method: Firewalls. * url-gateway-program-interactive: Firewalls. * url-gateway-telnet-program: Firewalls. * url-gateway-telnet-ready-regexp: Firewalls. * url-global-history-file: Basic Setup. * url-global-history-file: Global History. * url-keep-history: Global History. * url-keep-history: Session History. * url-mime-accept-string: Miscellaneous Functions. * url-passwd-entry-func: Other Variables. * url-personal-mail-address: Basic Setup. * url-pgp/pem-entity: Basic Setup. * url-request-data: Miscellaneous Functions. * url-request-extra-headers: Miscellaneous Functions. * url-request-method: Miscellaneous Functions. * url-show-status: Other Variables. * url-uncompressor-alist: Other Variables. * url-use-hypertext-dired: General Formatting. * url-use-hypertext-dired: Action. * url-use-hypertext-gopher: Basic Setup. * url-wais-gateway-port: Basic Setup. * url-wais-gateway-server: Basic Setup. * url-waisq-prog: Other Variables. * url-xterm-command: Basic Setup. * w3-allow-searching-of: Searching. * w3-annotation-mode: Personal Annotations. * w3-color-filter: Inlined images. * w3-color-max-blue: Inlined images. * w3-color-max-green: Inlined images. * w3-color-max-red: Inlined images. * w3-color-use-reducing: Inlined images. * w3-confirmation-func: Basic Setup. * w3-current-file: Global Variables. * w3-current-last-buffer: Global Variables. * w3-current-mime-headers: Global Variables. * w3-current-port: Global Variables. * w3-current-server: Global Variables. * w3-current-type: Global Variables. * w3-default-action: Basic Setup. * w3-default-homepage: Basic Setup. * w3-delay-image-loads: Basic Setup. * w3-delimit-emphasis: Basic Setup. * w3-delimit-emphasis: Character based terminals. * w3-delimit-links: Basic Setup. * w3-delimit-links: General Formatting. * w3-emacs19-hack-faces-p: Smart terminals. * w3-file-prepare-hooks: General Formatting. * w3-gopher-labels: General Formatting. * w3-graphic-converter-alist: Inlined images. * w3-header-chars-assoc: Character based terminals. * w3-horizontal-rule-char: General Formatting. * w3-hotlist-file: Hotlist Handling. * w3-hotlist-file: Hotlist Handling. * w3-hotlist-file: Hotlist Handling. * w3-hotlist-file: Basic Setup. * w3-hotlist-file: Hotlist Handling. * w3-html-entities: Miscellaneous Functions. * w3-html2latex-args: Miscellaneous. * w3-html2latex-prog: Miscellaneous. * w3-icon-directory-list: Other Variables. * w3-keep-history: Action. * w3-keep-old-buffers: Other Variables. * w3-latex-docstyle: Miscellaneous. * w3-link-end-delimiter: General Formatting. * w3-link-start-delimiter: General Formatting. * w3-list-chars-assoc: General Formatting. * w3-load-hooks: Hooks. * w3-personal-annotation-directory: Personal Annotations. * w3-personal-annotation-directory: Basic Setup. * w3-print-commnad: Miscellaneous. * w3-reuse-buffers: Other Variables. * w3-right-border: Basic Setup. * w3-right-border: General Formatting. * w3-running-epoch: Global Variables. * w3-running-FSF19: Global Variables. * w3-running-lemacs: Global Variables. * w3-running-new-lucid: Global Variables. * w3-show-headers: Other Variables. * w3-show-status: Other Variables. * w3-style-assoc: Graphics workstations. * w3-style-chars-assoc: Character based terminals. * w3-style-chars-assoc: Basic Setup. * w3-track-mouse: Basic Setup. * w3-use-forms-index: Basic Setup. * w3-use-html2latex: Miscellaneous. * w3-use-hypertext-gopher: General Formatting. * w3-working-buffer: Miscellaneous Functions.